RCS(1) Unix Programmer's Manual RCS(1) NNNAAAMMMEEE rcs - change RCS file attributes SSSYYYNNNOOOPPPSSSIIISSS rrrcccsss [ _o_p_t_i_o_n_s ] _f_i_l_e ... DDDEEESSSCCCRRRIIIPPPTTTIIIOOONNN rrrcccsss creates new RCS files or changes attributes of existing ones. An RCS file contains multiple revisions of text, an access list, a change log, descriptive text, and some control attributes. For rrrcccsss to work, the caller's login name must be on the access list, except if the access list is empty, the caller is the owner of the file or the superuser, or the ---iii option is present. File names ending in ,,,vvv denote RCS files; all others denote working files. If a working file is given, rrrcccsss tries to find the corresponding RCS file first in an RCS subdirectory and then in the working file's directory, as explained in cccooo(1). OOOPPPTTTIIIOOONNNSSS ---iii Create and initialize a new RCS file, but do not deposit any revision. If the RCS file has no path prefix, try to place it first into the subdirectory ...///RRRCCCSSS, and then into the current directory. If the RCS file already exists, print an error message. ---aaa_l_o_g_i_n_s Append the login names appearing in the comma-separated list _l_o_g_i_n_s to the access list of the RCS file. ---AAA_o_l_d_f_i_l_e Append the access list of _o_l_d_f_i_l_e to the access list of the RCS file. ---eee[logins]]] Erase the login names appearing in the comma-separated list _l_o_g_i_n_s from the access list of the RCS file. If _l_o_g_i_n_s is omitted, erase the entire access list. ---bbb[rev]]] Set the default branch to _r_e_v. If _r_e_v is omitted, the default branch is reset to the (dynamically) highest branch on the trunk. ---ccc_s_t_r_i_n_g sets the comment leader to _s_t_r_i_n_g. The comment leader is printed before every log message line generated by the keyword $$$LLLoooggg$$$ during checkout (see cccooo(1)). This is useful for programming languages without multi-line comments. An initial ccciii ,,, or an rrrcccsss\\\ ---iii without ---ccc, guesses the comment leader from the suffix of the working file. ---kkk_s_u_b_s_t Set the default keyword substitution to _s_u_b_s_t. The effect of keyword substitution is described in cccooo(1). Giving an explicit ---kkk option to cccooo, rrrcccsssdddiiiffffff, and rrrcccsssmmmeeerrrgggeee overrides this default. Beware rrrcccsss\\\ ---kkkvvv, because ---kkkvvv is incompatible with cccooo\\\ ---lll. Use rrrcccsss\\\ ---kkkkkkvvv to restore the normal default keyword substitution. \*(Dt 1 RCS(1) Unix Programmer's Manual RCS(1) ---lll[rev]]] Lock the revision with number _r_e_v. If a branch is given, lock the latest revision on that branch. If _r_e_v is omitted, lock the latest revision on the default branch. Locking prevents overlapping changes. A lock is removed with ccciii or rrrcccsss\\\ ---uuu (see below). ---uuu[rev]]] Unlock the revision with number _r_e_v. If a branch is given, unlock the latest revision on that branch. If _r_e_v is omitted, remove the latest lock held by the caller. Normally, only the locker of a revision may unlock it. Somebody else unlocking a revision breaks the lock. This causes a mail message to be sent to the original locker. The message contains a commentary solicited from the breaker. The commentary is terminated by end-of-file or by a line containing ...\ by itself. ---LLL Set locking to _s_t_r_i_c_t. Strict locking means that the owner of an RCS file is not exempt from locking for checkin. This option should be used for files that are shared. ---UUU Set locking to non-strict. Non-strict locking means that the owner of a file need not lock a revision for checkin. This option should _n_o_t be used for files that are shared. Whether default locking is strict is determined by your system administrator, but it is normally strict. ---nnnnnnaaammmeee[:rev] Associate the symbolic name _n_a_m_e with the branch or revision _r_e_v. Print an error message if _n_a_m_e is already associated with another number. If _r_e_v is omitted, the symbolic name is deleted. ---NNNnnnaaammmeee[:rev] Act like ---nnn, except override any previous assignment of _n_a_m_e. ---ooo_r_a_n_g_e deletes (outdates) the revisions given by _r_a_n_g_e. A range consisting of a single revision number means that revision. A range consisting of a branch number means the latest revision on that branch. A range of the form _r_e_v_1---_r_e_v_2 means revisions _r_e_v_1 to _r_e_v_2 on the same branch, ---_r_e_v means from the beginning of the branch containing _r_e_v up to and including _r_e_v, and _r_e_v--- means from revision _r_e_v to the end of the branch containing _r_e_v. None of the outdated revisions may have branches or locks. ---qqq Run quietly; do not print diagnostics. ---III Run interactively, even if the standard input is not a terminal. ---sssssstttaaattteee[:rev] Set the state attribute of the revision _r_e_v to _s_t_a_t_e . If _r_e_v is a branch number, assume the latest revision on that branch. If _r_e_v is omitted, assume the latest revision on the default branch. Any identifier is acceptable for _s_t_a_t_e. A useful set of states is EEExxxppp (for experimental), SSStttaaabbb (for stable), and RRReeelll (for released). By default, ccciii(1) sets the state of a revision to EEExxxppp. \*(Dt 2 RCS(1) Unix Programmer's Manual RCS(1) ---ttt[file]]] Write descriptive text from the contents of the named _f_i_l_e into the RCS file, deleting the existing text. The _f_i_l_e name may not begin with ---. If _f_i_l_e is omitted, obtain the text from standard input, terminated by end-of-file or by a line containing ...\ by itself. Prompt for the text if interaction is possible; see ---III. With ---iii, descriptive text is obtained even if ---ttt is not given. ---ttt---_s_t_r_i_n_g Write descriptive text from the _s_t_r_i_n_g into the RCS file, deleting the existing text. ---VVV_n Emulate RCS version _n. See cccooo(1) for details. CCCOOOMMMPPPAAATTTIIIBBBIIILLLIIITTTYYY The ---bbb_r_e_v option generates an RCS file that cannot be parsed by RCS version 3 or earlier. The ---kkk_s_u_b_s_t options (except ---kkkkkkvvv) generate an RCS file that cannot be parsed by RCS version 4 or earlier. Use rrrcccsss ---VVV_n to make an RCS file acceptable to RCS version _n by discarding information that would confuse version _n. DDDIIIAAAGGGNNNOOOSSSTTTIIICCCSSS The RCS file name and the revisions outdated are written to the diagnostic output. The exit status is zero if and only if all operations were successful. FFFIIILLLEEESSS rrrcccsss accesses files much as ccciii(1) does, except that it does not need to access the working file or its directory. IIIDDDEEENNNTTTIIIFFFIIICCCAAATTTIIIOOONNN Author: Walter F. Tichy. Revision Number: 5.3; Release Date: 1990/12/04. Copyright (c) 1982, 1988, 1989 by Walter F. Tichy. Copyright (c) 1990 by Paul Eggert. SSSEEEEEE AAALLLSSSOOO co(1), ci(1), ident(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(5) Walter F. Tichy, RCS--A System for Version Control, _S_o_f_t_w_a_r_e--_P_r_a_c_t_i_c_e & _E_x_p_e_r_i_e_n_c_e 111555, 7 (July 1985), 637-654. \*(Dt 3